Method and device for random access for beam failure recovery

ABSTRACT

A method for random access for beam failure recovery. In the method, a random access configuration for the beam failure recovery is received. In the event of a beam failure, a random access procedure is performed according to the random access configuration.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.16/089,351, filed Sep. 27, 2018, which is a National stage ofInternational Application No. PCT/CN2018/101051, filed Aug. 17, 2018,which claims priority to International Application No.PCT/CN2017/098093, filed Aug. 18, 2017, which are all herebyincorporated by reference.

TECHNICAL FIELD

The present disclosure relates generally to wireless access technology,and in particular, to a method for random access for beam failurerecovery and related terminal device and network device.

BACKGROUND ART

In a NR (New Radio) system, in order to improve coverage and increasedata rate, beamforming is widely used. With the beamforming, a networkdevice may transmit user specific data via narrow beam which can improveSINR (Signal to Interference plus Noise Ratio). Since the beam providesquite narrow coverage, it is possible that a user equipment (UE) may besuddenly out of the coverage of the beam. Thus the network device wouldnot be able to efficiently schedule the data to the UE and/or the UEwould not monitor the right beam (or beam link pair) used by the networkdevice to transmit a control channel (like PDCCH) and the UE would notbe able to detect the scheduled information. This problem is typicallycalled “beam failure”.

SUMMARY OF THE INVENTION

It is therefore an object of embodiments of the present disclosure toprovide a method for random access for beam failure recovery, which canimplement beam failure recovery using random access.

According to a first aspect of the disclosure, there is provided amethod in a user equipment for random access for beam failure recovery.In the method, specific random access configuration for the beam failurerecovery is received from a base station. In the event of a beamfailure, a random access procedure is performed according to thespecific random access configuration.

In some embodiments, at least one candidate beam with downlink qualityhigher than a first threshold is detected, and the random access isperformed via the respective at least one candidate beam.

In some embodiments, a candidate beam which has the highest downlinkquality of the at least one candidate beam is determined, and the randomaccess is performed via the determined candidate beam. If the randomaccess fails, another candidate beam of the at least one candidate beamis determined, and the random access is performed via the anothercandidate beam.

In some embodiments, it is determined whether the determined candidatebeam is configured with a contention free random access resource or acontention based random access resource. If it is determined that thedetermined candidate beam is configured with the contention free randomaccess resource, contention free random access is performed via thedetermined candidate beam. If it is determined that the determinedcandidate beam is configured with the contention based random accessresource, it is determined whether the downlink quality of thedetermined candidate beam is higher than that of any candidate beamconfigured with a contention free random access resource by a secondthreshold. If it is determined that the downlink quality of thedetermined candidate beam is higher than that of any candidate beamconfigured with the contention free random access resource by the secondthreshold, contention based random access is performed via thedetermined candidate beam. If it is determined that the downlink qualityof the determined candidate beam is not higher than that of anycandidate beam configured with the contention free random accessresource by the second threshold, contention free random access isperformed via the candidate beam configured with the contention freerandom access resource.

In some embodiments, if the random access procedure is stopped, anindication is generated that the random access procedure is for the beamfailure recovery.

In some embodiments, the random access procedure is stopped when amaximum number of preamble transmission attempts is reached or a radiolink failure timer expires.

In some embodiments, the specific random access configuration comprisesat least one of the following parameters: a maximum number of preambletransmission attempts, a size of random access response window, and acontention free random access resource.

In some embodiments, the contention free random access resource is setas a plurality of different random access resources reserved for thebeam failure recovery and/or one random access resource reserved for thebeam failure recovery with multiple attempts to use.

In some embodiments, the random access is performed before the pluralityof different random access resources is released or the multipleattempts are reached.

According to a second aspect of the disclosure, there is provided a userequipment. The user equipment comprises a processor and a memory, saidmemory containing instructions executable by said processor, wherebysaid user equipment is operative to receive specific random accessconfiguration for the beam failure recovery and to perform, in the eventof a beam failure, a random access procedure according to the specificrandom access configuration.

According to a third aspect of the disclosure, there is provided amethod in a base station for random access for beam failure recovery. Inthe method, specific random access configuration is set for the beamfailure recovery. Then the specific random access configuration istransmitted to a user equipment.

According to a fourth aspect of the disclosure, there is provided a basestation. The base station comprises a processor and a memory, saidmemory containing instructions executable by said processor, wherebysaid base station is operative to set specific random accessconfiguration for the beam failure recovery, and to transmit thespecific random access configuration.

According to a fifth aspect of the disclosure, there is provided acomputer readable storage medium having a computer program storedthereon. The computer program is executable by a device to cause thedevice to carry out the method for random access for beam failurerecovery according to the first aspect of the disclosure.

According to a sixth aspect of the disclosure, there is provided acomputer program product executable by a device to cause the device tocarry out the method for random access for beam failure recoveryaccording to the third aspect of the disclosure.

According to a seventh aspect of the disclosure, there is provide adevice for random access for beam failure recovery. The device comprisesa receiver configured to receive specific random access configurationfor the beam failure recovery, and a performing module configured toperform, in the event of a beam failure, a random access procedureaccording to the specific random access configuration.

According to an eighth aspect of the disclosure, there is provide adevice for random access for beam failure recovery. The device comprisesa setting module configured to set specific random access configurationfor the beam failure recovery, and a transmitter configured to transmitthe specific random access configuration.

It is an advantage that the method for random access according to theembodiments can utilize the specific random access configuration toimplement the beam failure recovery through the random access procedure.Moreover, the random access procedure based on the specific randomaccess configuration can increase the success of the beam failurerecovery and reduce the delay of the beam failure recovery. In addition,the method can minimize negative impact on performance of the terminaldevice due to failure of the beam recovery.

BRIEF DESCRIPTION OF THE DRAWINGS

Through the more detailed description of some embodiments of the presentdisclosure in the accompanying drawings, the above and other objects,features and advantages of the present disclosure will become moreapparent, wherein the same reference generally refers to the samecomponents in the embodiments of the present disclosure. The drawingsare illustrated for facilitating better understanding of the embodimentsof the disclosure and not necessarily drawn to scale, in which:

FIG. 1 is a flowchart illustrating the method for random access for beamfailure recovery according to some embodiments of the presentdisclosure;

FIG. 2 is a flowchart illustrating an exemplary process of random accessaccording to some embodiments of the present disclosure;

FIG. 3 is a diagram illustrating another exemplary process of randomaccess according to some embodiments of the present disclosure;

FIG. 4 is a flowchart illustrating the method for random access for beamfailure recovery according to some embodiments of the presentdisclosure;

FIG. 5 is a schematic block diagram of the terminal device according tosome embodiments of the present disclosure;

FIG. 6 is a schematic block diagram of the network device according tosome embodiments of the present disclosure; and

FIG. 7 is a schematic block diagram of a device for random access forbeam failure recovery according to some embodiments of the presentdisclosure; and

FIG. 8 is a schematic block diagram of a device for random access forbeam failure recovery according to some embodiments of the presentdisclosure.

DETAILED DESCRIPTION

Some preferable embodiments will be described in more detail withreference to the accompanying drawings, in which the preferableembodiments of the present disclosure have been illustrated. However,the present disclosure can be implemented in various manners, and thusshould not be construed to be limited to the embodiments disclosedherein. On the contrary, those embodiments are provided for the thoroughand complete understanding of the present disclosure, and completelyconveying the scope of the present disclosure to those skilled in theart.

As used herein, the term “wireless communication network” refers to anetwork following any suitable communication standards, such asLTE-Advanced (LTE-A), LTE, Wideband Code Division Multiple Access(WCDMA), High-Speed Packet Access (HSPA), and so on. Furthermore, thecommunications between a terminal device and a network device in thewireless communication network may be performed according to anysuitable generation communication protocols, including, but not limitedto, Global System for Mobile Communications (GSM), Universal MobileTelecommunications System (UMTS), Long Term Evolution (LTE), and/orother suitable, and/or other suitable the first generation (1G), thesecond generation (2G), 2.5G, 2.75G, the third generation (3G), thefourth generation (4G), 4.5G, the future fifth generation (5G)communication protocols, wireless local area network (WLAN) standards,such as the IEEE 802.11 standards; and/or any other appropriate wirelesscommunication standard, such as the Worldwide Interoperability forMicrowave Access (WiMax), Bluetooth, and/or ZigBee standards, and/or anyother protocols either currently known or to be developed in the future.

The term “network device” refers to a device in a wireless communicationnetwork via which a terminal device accesses the network and receivesservices therefrom. The network device refers a base station (BS), anaccess point (AP), or any other suitable device in the wirelesscommunication network. The BS may be, for example, a node B (NodeB orNB), an evolved NodeB (eNodeB or eNB), or gNB, a Remote Radio Unit(RRU), a radio header (RH), a remote radio head (RRH), a relay, a lowpower node such as a femto, a pico, and so forth. Yet further examplesof the network device may include multi-standard radio (MSR) radioequipment such as MSR BSs, network controllers such as radio networkcontrollers (RNCs) or base station controllers (BSCs), base transceiverstations (BTSs), transmission points, transmission nodes. Moregenerally, however, the network device may represent any suitable device(or group of devices) capable, configured, arranged, and/or operable toenable and/or provide a terminal device access to the wirelesscommunication network or to provide some service to a terminal devicethat has accessed the wireless communication network.

The term “terminal device” refers to any end device that can access awireless communication network and receive services therefrom. By way ofexample and not limitation, the terminal device refers to a mobileterminal, user equipment (UE), or other suitable devices. The UE may be,for example, a Subscriber Station (SS), a Portable Subscriber Station, aMobile Station (MS), or an Access Terminal (AT). The terminal device mayinclude, but not limited to, portable computers, image capture terminaldevices such as digital cameras, gaming terminal devices, music storageand playback appliances, a mobile phone, a cellular phone, a smartphone, voice over IP (VoIP) phones, wireless local loop phones, atablet, a wearable device, a personal digital assistant (PDA), portablecomputers, desktop computer, image capture terminal devices such asdigital cameras, gaming terminal devices, music storage and playbackappliances, wearable terminal devices, vehicle-mounted wireless terminaldevices, wireless endpoints, mobile stations, laptop-embedded equipment(LEE), laptop-mounted equipment (LME), USB dongles, smart devices,wireless customer-premises equipment (CPE) and the like. In thefollowing description, the terms “terminal device”, “terminal”, “userequipment” and “UE” may be used interchangeably. As one example, aterminal device may represent a UE configured for communication inaccordance with one or more communication standards promulgated by the3rd Generation Partnership Project (3GPP), such as 3GPP's GSM, UMTS,LTE, and/or 5G standards. As used herein, a “user equipment” or “UE” maynot necessarily have a “user” in the sense of a human user who ownsand/or operates the relevant device. In some embodiments, a terminaldevice may be configured to transmit and/or receive information withoutdirect human interaction. For instance, a terminal device may bedesigned to transmit information to a network on a predeterminedschedule, when triggered by an internal or external event, or inresponse to requests from the wireless communication network. Instead, aUE may represent a device that is intended for sale to, or operation by,a human user but that may not initially be associated with a specifichuman user.

The terminal device may support device-to-device (D2D) communication,for example by implementing a 3GPP standard for sidelink communication,and may in this case be referred to as a D2D communication device.

As yet another example, in an Internet of Things (IOT) scenario, aterminal device may represent a machine or other device that performsmonitoring and/or measurements, and transmits the results of suchmonitoring and/or measurements to another terminal device and/or networkequipment. The terminal device may in this case be a machine-to-machine(M2M) device, which may in a 3GPP context be referred to as amachine-type communication (MTC) device. As one particular example, theterminal device may be a UE implementing the 3GPP narrow band internetof things (NB-IoT) standard. Particular examples of such machines ordevices are sensors, metering devices such as power meters, industrialmachinery, or home or personal appliances, for example refrigerators,televisions, personal wearables such as watches etc. In other scenarios,a terminal device may represent a vehicle or other equipment that iscapable of monitoring and/or reporting on its operational status orother functions associated with its operation.

As used herein, a downlink, DL transmission refers to a transmissionfrom the network device to a terminal device, and an uplink, ULtransmission refers to a transmission in an opposite direction.

References in the specification to “one embodiment,” “an embodiment,”“an example embodiment,” and the like indicate that the embodimentdescribed may include a particular feature, structure, orcharacteristic, but it is not necessary that every embodiment includesthe particular feature, structure, or characteristic. Moreover, suchphrases are not necessarily referring to the same embodiment. Further,when a particular feature, structure, or characteristic is described inconnection with an embodiment, it is submitted that it is within theknowledge of one skilled in the art to affect such feature, structure,or characteristic in connection with other embodiments whether or notexplicitly described.

It shall be understood that although the terms “first” and “second” etc.may be used herein to describe various elements, these elements shouldnot be limited by these terms. These terms are only used to distinguishone element from another. For example, a first element could be termed asecond element, and similarly, a second element could be termed a firstelement, without departing from the scope of example embodiments. Asused herein, the term “and/or” includes any and all combinations of oneor more of the associated listed terms.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be liming of exampleembodiments. As used herein, the singular forms “a”, “an” and “the” areintended to include the plural forms as well, unless the context clearlyindicates otherwise. It will be further understood that the terms“comprises”, “comprising”, “has”, “having”, “includes” and/or“including”, when used herein, specify the presence of stated features,elements, and/or components etc., but do not preclude the presence oraddition of one or more other features, elements, components and/orcombinations thereof.

In the following description and claims, unless defined otherwise, alltechnical and scientific terms used herein have the same meaning ascommonly understood by one of ordinary skills in the art to which thisdisclosure belongs.

3GPP has acknowledged the importance of the beam failure problem andstarted to discuss for 5G system a procedure called “beam recovery” upondetection of a beam failure for UEs in RRC_CONNECTED state. In the beamrecovery, the UE in RRC_CONNECTED state would perform measurementsassociated to the quality of the serving link and, if the quality goesbelow a given threshold, the UE would perform beam recovery. Theprocedure aims to solve the situation where TX and/or RX beams of thenetwork device such as gNodeB and the UE have become misaligned, butthere are additional beams that could be used to maintain the connectionbetween the gNodeB and the UE.

The beam failure recovery procedure may include the following aspects:

-   -   Beam failure detection: the UE may monitor a certain periodic        reference signal (RS) to estimate the quality of the serving        link. Once the quality of the serving link falls below a certain        threshold, which means a beam failure occurs, the UE may        initiate the beam recovery.    -   New candidate beam identification: Once the beam failure has        been detected, the UE may identify a new candidate beam that        would provide adequate quality. The UE then searches for a        specific RS, which is transmitted from the same network device        but in different candidate beams. During this search procedure,        the UE may also change its RX beam.    -   Beam failure recovery request: Once the new candidate beam has        been found, the UE may transmit an uplink (UL) signal using        certain UL resources. The gNodeB may receive the UL signal in        these UL resources, and can determine which candidate beam the        UE identified based on the received UL signal.    -   Beam failure recovery response: When the gNodeB has received the        beam failure recovery request, it sends a downlink (DL) response        to indicate to the UE that it received the request using the        knowledge of the new beam. The UE may monitor the response to        the beam failure recovery request. Once the UE has successfully        received the response, the beam recovery is complete.

Currently, it is proposed that a random access procedure may be used forthe beam failure recovery. It is known that the random access procedureis not designed as a recovery procedure but as an ordinary procedure tobe triggered during an initial access to a wireless network of the UE,e.g. when the UE is turned on, or during a transition from RRC_IDLEstate and/or RRC_INACTIVE state to RRC_CONNECTED state of the UE, andduring a handover execution. Considering the ordinary random accessprocedure also requires a beam selection mechanism, as required in thebeam failure recovery, therefore the random access procedure may also beused for beam failure recovery. The beam is recovered when the randomaccess procedure is successful. Additionally, both a content free randomaccess procedure and a contention based random access procedure may beused to recover the beam.

However, due to the different purposes of the random access procedure,there may be some problems if the UE has to perform the beam failurerecovery according to the same random access configuration and procedureas the ordinary random access procedure. Now there are quite a lotdetails about the random access for the beam failure recovery notsettled.

In view of the above, embodiments of the present disclosure provide anew random access mechanism specific for beam failure recovery.

FIG. 1 shows a flowchart illustrating the method for random access forbeam failure recovery according to some embodiments of the disclosure.This method may be performed by a terminal device in a wirelesscommunication network with beamforming. The wireless communicationnetwork may be, for example, a LTE (Long Term Evolution) system, or a NRsystem, etc. The terminal device may be a user equipment, such as amobile phone, a smart phone, a wearable device, a tablet, and the like.

As shown in FIG. 1, at block 110, the terminal device may receivespecific random access configuration for the beam failure recovery. Thespecific random access configuration may comprise same parameters asthose in the random access configuration for the ordinary random accessprocedure, but in the specific random access configuration, some of theparameters are reconfigured to be different from the ordinary randomaccess procedure, which will be described later. Moreover, the specificrandom access configuration may be received from a network device (e.g.a base station in the NR system, e.g. gNodeB) via dedicated signaling.

To facilitate understanding, the random access configuration will befirst briefly introduced. The random access configuration may include atleast the following:

1) RACH-ConfigCommon

-   -   Preamble information        -   Number of preambles (numberOfRA-Preambles): Number of            non-dedicated random access preambles as defined in the MAC            specifications TS 36.321 encoded as an integer value. In            LTE, there can be a maximum number of 64 preambles, while in            NR a higher number may be expected. Less preambles for            common random access channel (RACH) may increase the number            of preambles to be assigned for dedicated access and/or can            potentially reduce the detection complexity at the network            side (as fewer preambles need to be detected).    -   Preamble group configurations: It consists of size of preambles,        message size and message power offsets.    -   Power ramping parameters (PowerRampingParameters): In LTE, it        consists of a powerRampingStep and a        preambleInitialReceivedTargetPower. In NR, similar parameters        are expected. In addition, there could also exist something        related to the number of attempts before the UE switches to        another Tx or Rx beam.    -   Random access supervision parameters        -   Maximum number of preamble transmission attempts            (preambleTransMax): In LTE, the preambleTransMax is the            number of timers the UE should try to send a preamble            without necessary decoding a random access response (RAR)            successfully.        -   Size of RAR window (ra-ResponseWindowSize): In LTE, the            ra-ResponseWindowSize is defined as the duration of the RA            response window in TS 36.321 where the value is provided in            subframes.        -   Timer for contention resolution            (mac-ContentionResolutionTimer).    -   Maximum number of HARQ for MSG.3 (maxHARQ-Msg3Tx): In LTE, the        parameters maxHARQ-Msg3Tx defines the Msg3 HARQ transmissions in        TS 36.321 used for contention based random access.    -   Additional parameters that may exist in NR: As a DL beam        transmitted by the network device and detected by the UE by        detection of a synchronization signal (SS) block and a SS block        identifier, there could also be CSI-RS (Channel State        Information Reference Signal) to RACH mapping.

2) RACH-ConfigDedicated

-   -   Preamble index    -   PRACH Mask Index

In some embodiments, the specific random access configuration maycomprise contention based random access configuration (e.g.RACH-ConfigCommon) and the contention free random access configuration(e.g. RACH-ConfigDedicated). In the specific random accessconfiguration, the following parameters may be configured to be specificto the beam failure recovery and different from the ordinary randomaccess procedure:

-   -   Maximum number of preamble transmission attempts: For the random        access procedure for the beam failure recovery, there could be a        radio link failure (RLF) timer running. When the RLF timer        expires, the terminal device should do cell reselection to find        a suitable cell, instead of recovering the beam in the original        cell. Therefore, the maximum number of preamble transmission        attempts for the beam failure recovery should take the RLF timer        into account and may be set different from the ordinary random        access procedure. Moreover, the random access procedure for the        beam failure recovery will be stopped if the maximum number of        preamble transmission attempts is reached or the RLF timer        expires. For example, if the RLF timer expires, the terminal        device cannot continue the random access for the beam failure        recovery, even if the maximum number of preamble transmission        attempts has not been reached. If the maximum number of preamble        transmission attempts is reached but the RLF timer does not        expire, the random access procedure for the beam failure        recovery will also be stopped.    -   Size of RAR window: As described above, the size of RAR window        is the duration of receiving the RAR from the network device. In        order to speed up the beam failure recovery, the size of RAR        window may be set different from the ordinary random access        procedure. For example, the size of RAR window may be set        shorter. When the network device identifies a preamble signal        from the terminal device that is used for the beam failure        recovery, the network device may send a response more quickly        than the ordinary random access procedure.    -   Resource for contention free random access (also referred to as        “contention free random access resource”): In the ordinary        random access procedure, the reserved contention free random        access resource cannot be reused if the contention free random        access fails. But in the beam failure recovery, there may be        multiple candidate beams suitable for the beam failure recovery.        Therefore, it is expected that the contention free random access        can be continued via a different candidate beam when the        previous random access fails. Thus in the specific random access        configuration, the contention free random access resource may be        set as a plurality of different random access resources reserved        for the beam failure recovery and/or one random access resource        reserved for the beam failure recovery with multiple attempts to        use. The terminal device may perform the contention free random        access multiple times using the different random access        resources reserved for the beam failure recovery or the same        random access resource reserved for the beam failure recovery.

Then at block 120, in the event of a beam failure, the terminal devicemay perform a random access procedure according to the received specificrandom access configuration. FIG. 2 illustrates an exemplary process ofrandom access according to some embodiment of the present disclosures.

As shown in FIG. 2, at block 205, when a beam failure occurs, e.g. theterminal device moves out of its serving beam, the terminal device maydetect at least one candidate beam that is suitable for the beam failurerecovery. The candidate beam has a downlink quality higher than a giventhreshold (i.e. first threshold). The downlink quality may berepresented by a Reference Signal Received Power (RSRP).

Then the terminal device may perform the random access via therespective at least one candidate beam. In some embodiments, at block210, the terminal device may determine a candidate beam with the highestdownlink quality of the detected at least one candidate beam, which canbe referred to as “a best candidate beam”. Then at block 215, theterminal device may perform random access via the best candidate beam.If the random access is successful (i.e. “Y” of block 218), at block220, the best candidate beam becomes the new serving beam of theterminal device, and the terminal device may communicate with thenetwork device via the new serving beam. If the random access fails(i.e. “N” of block 218), the terminal device may check whether the RLFtimer expires at block 225. If the RLF timer expires, the random accessprocedure for beam failure recovery is stopped at block 230. If the RLFtimer does not expire, the terminal device may check whether the maximumnumber of preamble transmission attempts is reached at block 235. If themaximum number of preamble transmission attempts is reached, the randomaccess procedure for beam failure recovery is stopped at block 230. Ifthe maximum number of preamble transmission attempts is not reached, atblock 240, the terminal device may determine another candidate beam (ifany) of the detected at least one candidate beam. This candidate beammay have the second highest downlink quality. Then at block 245, theterminal device may perform the random access via this candidate beam.If the random access fails, the terminal may repeatedly perform blocks218 to 245 until the random access is successful or the maximum numberof preamble transmission attempts is reached or the RLF timer expires.

In some embodiments, the candidate beam may be used for the randomaccess for the beam failure recovery more than once. For example, thereare two candidate beams and the maximum number of preamble transmissionattempts is four. Then if the random accesses via the two candidatebeams both fail, but the maximum number of preamble transmissionattempts is not reached. The two candidate beams may be used again forthe random access if the downlink quality is still above the firstthreshold. For the contention free random access, different reservedrandom access resources or the same reserved random access resource (ifthe number of attempts is not reached) may be utilized.

In some embodiments, the terminal device may detect the candidatebeam(s) continuously. In this way, the terminal device may select thecurrent best candidate beam every time when performing the randomaccess.

In some embodiments, when the random access procedure for the beamfailure recovery is stopped, the terminal device may generate anindication to a higher layer that the random access procedure is for thebeam failure recovery. In the ordinary random access procedure, when themaximum number of preamble transmission attempts is reached, MAC layerof the terminal device may send an indication of the random accessfailure to RRC layer of the terminal device which then declares theradio link failure. Then a RRC connection reestablishment procedure maybe triggered. For the random access procedure for the beam failurerecovery, there is the RLF timer to trigger the radio link failure. Whenthe RLF timer expires, the RRC connection reestablishment procedure willbe triggered. Therefore, it is not necessary for the RRC layer todeclare the radio link failure. When the RRC layer receives theindication from the MAC layer which indicates that the random accessprocedure is for the beam failure recovery, RRC layer does nothing.

In some cases, in the wireless system, some beams are configured withthe contention free random access resources, and some beams areconfigured with the contention based random access resources. FIG. 3shows another exemplary process of the random access implementable insuch the wireless system.

In FIG. 3, when the terminal device determines a candidate beam for thebeam failure recovery (at block 305), at block 310, the terminal devicemay determine whether the determined candidate beam is configured withthe contention free random access resource or the contention basedrandom access resource. As described above, the terminal device hasalready received the specific random access configuration whichcomprises the configuration of the contention free random accessresource. The terminal device may make this determination based on thespecific random access configuration. Then at block 320, in response tothe determination that the candidate beam is configured with thecontention free random access resource, the terminal device may performthe contention free random access via the determined candidate beam. Ifthe candidate beam is configured with the contention based random accessresource, at block 330, the terminal device may determine whether thedownlink quality of the determined candidate beam is higher than that ofany candidate beam configured with the contention free random accessresource by a second threshold, e.g. N dB. If the determined candidatebeam has N dB higher downlink quality than any candidate beam with thecontention free random access resource, the terminal device may performthe contention based random access via the determined candidate beam, atblock 340. If the downlink quality of the determined candidate beam isnot higher than any candidate beam with the contention free randomaccess resource by N dB, the terminal device may select anothercandidate beam with the contention free random access resource, e.g. thebest candidate beam with the highest downlink quality of the candidatebeams with the contention free random access resource, and perform thecontention free random access via the selected candidate beam, at block350.

If the random access is successful, the determined candidate beambecomes the serving beam of the terminal device via which the terminaldevice may communicate with the network device. If the random accessfails, the terminal device may continue the random access until therandom access procedure is successful or stopped.

It can be seen from the above description that the method for randomaccess for beam failure recovery according to the above embodiments canimplement the beam failure recovery through the random access procedureaccording to the specific random access configuration. With the specificrandom access configuration, the success of the beam failure recoverycan be increased and the delay of the beam failure recovery can bereduced. In addition, the negative impact on the performance of theterminal device due to the failure of the beam recovery can beminimized.

FIG. 4 is a flowchart illustrating the method for random access for beamfailure recovery according to some embodiments of the presentdisclosure. The method may be performed by a network device. The networkdevice may be a base station in the wireless system, e.g. eNodeB in theLTE system, or gNodeB in the NR system.

As shown in FIG. 4, at block 410, the network device may set specificrandom access configuration for the beam failure recovery. In someembodiments, the network device may set the maximum number of preambletransmission attempts, the size of random access response window, andthe contention free random access resource specific to the beam failurerecovery in the specific random access configuration. The contentionfree random access resource may be set as a plurality of differentrandom access resources reserved for the beam failure recovery and/orone random access resource reserved for the beam failure recovery withmultiple attempts to use.

Then at block 420, the network device may transmit the specific randomaccess configuration. The network device may transmit the contentionbased random access configuration (e.g. RACH-ConfigCommon) and thecontention free random access configuration (e.g. RACH-ConfigDedicated)to the terminal device via dedicated signaling.

The method for random access for beam failure recovery according to theembodiments as described above may be applicable in many kinds ofapplications such as URLLC (Ultra Reliable and Low LatencyCommunication), MTC (Machine Type of Communication), eMBB (enhancedMobile Broadband), or mMTC (Massive Machine Type of Communication). Theparameters of the specific random access configuration may be configureddepending on which kind of application the terminal device operates.

FIG. 5 is a schematic block diagram of the terminal device 500 accordingto some embodiments of the present disclosure. The terminal device 500may be a user equipment, a mobile phone, a wearable device, a tablet, avehicle with radio communication functionality, or any other electronicdevice with radio communication functionality. As shown in FIG. 5, theterminal device 500 may comprise a processor 501 and a memory 502. Thememory 502 may contain instructions executable by the processor 501. Theterminal device 500 is operative to receive specific random accessconfiguration for the beam failure recovery, and to perform, in theevent of a beam failure, a random access procedure according to thespecific random access configuration.

The processor 501 may be of any type suitable to the local technicalenvironment, and may comprise one or more of general purpose computers,special purpose computers, microprocessors, digital signal processors(DSPs) and processors based on multi-core processor architectures, asnon-limiting examples. The terminal device 500 may have multipleprocessors, such as an application specific integrated circuit chip thatis slaved in time to a clock which synchronizes the main processor.

The memory 502 may be of any type suitable to the local technicalenvironment and may be implemented using any suitable data storagetechnology, such as semiconductor based memory devices, flash memory,magnetic memory devices and systems, optical memory devices and systems,fixed memory and removable memory, as non-limiting examples. The memory520 stores at least a part of a program. In addition, the terminaldevice 500 may further comprise a transceiver 503 operable forbidirectional communications. The transceiver 503 has one or moreantenna(s) to facilitate communication. The communication interface mayrepresent any interface that is necessary for communication with othernetwork elements. The program is assumed to include program instructionsthat, when executed by the associated processor 501, enable the terminaldevice 500 to operate in accordance with the embodiments of the presentdisclosure, as discussed herein with reference to FIGS. 1 to 3. That is,embodiments of the present disclosure can be implemented by computersoftware executable by the processor 501 of the terminal device 500, orby hardware, or by a combination of software and hardware.

In some embodiments, the terminal device 500 is further operative todetect at least one candidate beam with downlink quality higher than afirst threshold, and to perform the random access via the respective atleast one candidate beam.

In some embodiments, the terminal device 500 is further operative todetermine a candidate beam of the at least one candidate beam which hasthe highest downlink quality, to perform the random access via thedetermined candidate beam, to determine, if the random access fails,another candidate beam of the at least one candidate beam, and toperform the random access via the another candidate beam.

In some embodiments, the terminal device 500 is operative to determinewhether the determined candidate beam is configured with contention freerandom access resource or contention based random access resource, toperform, if it is determined that the determined candidate beam isconfigured with contention free random access resource, contention freerandom access via the determined candidate beam, to determine, if it isdetermined that the determined candidate beam is configured withcontention based random access resource, whether the downlink quality ofthe determined candidate beam is higher than that of any candidate beamconfigured with contention free random access resource by a secondthreshold, to perform, if it is determined that the downlink quality ofthe determined candidate beam is higher than that of any candidate beamconfigured with contention free random access resource by the secondthreshold, contention based random access via the determined candidatebeam, and to perform, if it is determined that the downlink quality ofthe determined candidate beam is not higher than that of any candidatebeam configured with contention free random access resource by thesecond threshold, contention free random access via the candidate beamconfigured with contention free random access resource.

In some embodiments, the terminal device 500 is further operative togenerate, if the random access procedure is stopped, an indication to ahigher layer that the random access procedure is for the beam failurerecovery.

In some embodiments, the terminal device 500 is operative to stop therandom access procedure when a maximum number of preamble transmissionattempts is reached or a radio link failure timer expires.

FIG. 6 is a schematic block diagram of the network device 600 accordingto some embodiments of the present disclosure. The network device may bea base station in the wireless system, e.g. eNodeB in the LTE system, orgNodeB in the NR system. As shown in FIG. 6, the network device 600 maycomprise a processor 601 and a memory 602. The memory 602 may containinstructions executable by the processor 601. The network device 600 isoperative to set specific random access configuration for the beamfailure recovery and to transmit the specific random accessconfiguration.

The processor 601 may be of any type suitable to the local technicalenvironment, and may comprise one or more of general purpose computers,special purpose computers, microprocessors, digital signal processors(DSPs) and processors based on multi-core processor architectures, asnon-limiting examples. The network device 600 may have multipleprocessors, such as an application specific integrated circuit chip thatis slaved in time to a clock which synchronizes the main processor. Thememory 602 may be of any type suitable to the local technicalenvironment and may be implemented using any suitable data storagetechnology, such as semiconductor based memory devices, flash memory,magnetic memory devices and systems, optical memory devices and systems,fixed memory and removable memory, as non-limiting examples. The memory620 stores at least a part of a program. In some embodiments, thenetwork device 600 may further comprise a transceiver 603 operative totransmit signals to and receive signals from the terminal device, and anetwork interface 604 operative to communicate signals with backendnetwork elements. The transceiver 603 is for bidirectionalcommunications. The transceiver 603 has one or more antenna(s) tofacilitate communication. The communication interface may represent anyinterface that is necessary for communication with other networkelements. The program is assumed to include program instructions that,when executed by the associated processor 601, enable the network device600 to operate in accordance with the embodiments of the presentdisclosure, as discussed herein with reference to FIG. 3. That is,embodiments of the present disclosure can be implemented by computersoftware executable by the processor 601 of the terminal device 600, orby hardware, or by a combination of software and hardware.

In some embodiments, the network device 600 is operative to set thespecific random access configuration including at least one of thefollowing parameters: a maximum number of preamble transmissionattempts, a size of random access response window, and a contention freerandom access resource.

FIG. 7 is a schematic block diagram of a device 700 for random accessfor beam failure recovery according to some embodiments of the presentdisclosure. The device 700 may be a terminal device such as a userequipment. As shown in FIG. 7, the device 700 may comprise a receiver701 configured to receive specific random access configuration for thebeam failure recovery, and a performing module 702 configured toperform, in the event of a beam failure, a random access procedureaccording to the specific random access configuration.

FIG. 8 is a schematic block diagram of a device 800 for random accessfor beam failure recovery according to some embodiments of the presentdisclosure. The device 800 may be a network device such as a basestation. As shown in FIG. 8, the device 800 may comprise a settingmodule 801 configured to set specific random access configuration forthe beam failure recovery, and a transmitter 802 configured to transmitthe specific random access configuration.

It should be noted that FIGS. 7, 8 merely illustrates various functionalmodules in the devices 700, 800, and a person skilled in the art canimplement these functional modules in practice using any suitablesoftware and hardware. Thus, the embodiments herein are generally notlimited to the shown structure of the devices 700, 800 and functionalmodules.

In some embodiments of the present disclosure, there is also provided acomputer readable storage medium having a computer program storedthereon. The computer program is executable by a device to cause thedevice to carry out the above method for beam failure recovery.

In some embodiments of the present disclosure, there is also provided acomputer program product executable by a device to cause the device tocarry out the method for beam failure recovery according to someembodiments of the present disclosure.

In general, the various exemplary embodiments may be implemented inhardware or special purpose circuits, software, logic or any combinationthereof. For example, some aspects may be implemented in hardware, whileother aspects may be implemented in firmware or software that may beexecuted by a controller, microprocessor or other computing device,although the disclosure is not limited thereto. While various aspects ofthe exemplary embodiments of this disclosure may be illustrated anddescribed as block diagrams, flow charts, or using some other pictorialrepresentation, it is well understood that these blocks, apparatus,systems, techniques or methods described herein may be implemented in,as non-limiting examples, hardware, software, firmware, special purposecircuits or logic, general purpose hardware or controller or othercomputing devices, or some combination thereof.

As such, it should be appreciated that at least some aspects of theexemplary embodiments of the disclosure may be practiced in variouscomponents such as integrated circuit chips and modules. It should thusbe appreciated that the exemplary embodiments of this invention may berealized in an apparatus that is embodied as an integrated circuit,where the integrated circuit may comprise circuitry (as well as possiblyfirmware) for embodying at least one or more of a data processor, adigital signal processor, baseband circuitry and radio frequencycircuitry that are configurable so as to operate in accordance with theexemplary embodiments of this disclosure.

It should be appreciated that at least some aspects of the exemplaryembodiments of the disclosure may be embodied in computer-executableinstructions, such as in one or more program modules, executed by one ormore computers or other devices. Generally, program modules compriseroutines, programs, objects, components, data structures, etc. thatperform particular tasks or implement particular abstract data typeswhen executed by a processor in a computer or other device. The computerexecutable instructions may be stored on a computer readable medium suchas a hard disk, optical disk, removable storage media, solid statememory, RAM, etc. As will be appreciated by those skilled in the art,the functionality of the program modules may be combined or distributedas desired in various embodiments. In addition, the functionality may beembodied in whole or in part in firmware or hardware equivalents such asintegrated circuits, field programmable gate arrays (FPGA), and thelike.

The present disclosure comprises any novel feature or combination offeatures disclosed herein either explicitly or any generalizationthereof. Various modifications and adaptations to the foregoingexemplary embodiments of this disclosure may become apparent to thoseskilled in the relevant arts in view of the foregoing description, whenread in conjunction with the accompanying drawings. However, any and allmodifications will still fall within the scope of the non-limiting andexemplary embodiments of this disclosure.

What is claimed is:
 1. A method in a user equipment in a networkcomprising: receiving a message comprising a random access configurationfor beam failure recovery from the network, wherein the random accessconfiguration comprises at least a maximum number of preambletransmission attempts; determining a beam failure event; performing arandom access procedure for beam failure recovery using the randomaccess configuration, the random access procedure comprises: selectingat least one candidate beam with a Reference Signal Received Power(RSRP) higher than a threshold; and attempting random access via theselected at least one candidate beam with the RSRP higher than thethreshold by sequencing through each selected at least one candidatebeam from highest RSRP to lowest RSRP, including re-attempting therandom access via one or more of the selected at least one candidatebeam; and stopping the random access procedure when: the random accessprocedure is successful; a radio link failure (RLF) timer expires; orthe maximum number of the preamble transmission attempts is reachedprior to the RLF timer expiring.
 2. The method according to claim 1,wherein the random access configuration further comprises one or more ofthe following parameters: a size of random access response window; and acontention free random access resource.
 3. The method according to claim1 further comprising: generating an indication that the random accessprocedure is for the beam failure recovery.
 4. A user equipmentcomprising: a processor; and a memory containing instructions which,when executed by said processor, cause said user equipment to: receive amessage comprising a random access configuration for beam failurerecovery from a network, wherein the random access configurationcomprises at least a maximum number of preamble transmission attempts;determine a beam failure event; perform a random access procedure forbeam failure recovery using the random access configuration, the randomaccess procedure to: select at least one candidate beam with a ReferenceSignal Received Power (RSRP) higher than a threshold; and attempt randomaccess via the selected at least one candidate beam with the RSRP higherthan the threshold by sequencing through each selected at least onecandidate beam from highest RSRP to lowest RSRP, including re-attemptingthe random access via one or more of the selected at least one candidatebeam; and stop the random access procedure when: the random accessprocedure is successful; a radio link failure (RLF) timer expires; orthe maximum number of the preamble transmission attempts is reachedprior r expiring.
 5. The user equipment according to claim 4, whereinthe random access configuration further comprises one or more of thefollowing parameters: a size of random access response window; and acontention free random access resource.
 6. The user equipment accordingto claim 4, wherein the user equipment is further to generate anindication that the random access procedure is for the beam failurerecovery.
 7. A base station comprising: a processor; and a memorycontaining instructions which, when executed by said processor, causesaid base station to: set a random access configuration for beam failurerecovery, wherein the random access configuration comprises at least amaximum number of preamble transmission attempts; and transmit a messagecomprising the random access configuration for beam failure recovery toa user equipment (UE), in order for the UE to determine a beam failureevent, and in order for the UE to perform a random access procedure forbeam failure recovery using the random access configuration, the randomaccess procedure to: select at least one candidate beam with a ReferenceSignal Received Power (RSRP) higher than a threshold; and attempt randomaccess via the selected at least one candidate beam with the RSRP higherthan the threshold by sequencing through each selected at least onecandidate beam from highest RSRP to lowest RSRP, including re-attemptingthe random access via one or more of the selected at least one candidatebeam; wherein the UE stops the random access procedure when: the randomaccess procedure is successful; a radio link failure (RLF) timerexpires; or the maximum number of the preamble transmission attempts isreached prior to the RLF timer expiring.
 8. The base station accordingto claim 7, wherein the random access configuration further comprisesone or more of the following parameters: a size of random accessresponse window; and a contention free random access resource.
 9. Thebase station according to claim 7, wherein the base station is furtherto receive an indication that the random access procedure is for thebeam failure recovery.